Oemdata.Adding data to OEM description for IO interface

Product : ISaGRAF V3

Date : 5-March-1996

File : Oemdata.Adding data to OEM description for IO interface.htm

Subject : Adding data to OEM standard description for IO interface

Keywords: OEM data - I/O data - I/O configuration tool

____________________________________________________________________

In some applications, it can be required to complete the description

of IO boards and IO channels (variables) with auxiliary data

provided by a separate tool. This document gives guidelines for such

an implementation.

The ISaGRAF target IO system requires the following information,

normally built by the Code Generator:

- Relationship between variable and IO connection

(slot number / channel index)

- Type and direction must be coherent between variable

and corresponding IO board

- Board OEM key code

This is the minimum required information. Such fields are naturally

stored in the target IO data base, and must be described in the

application IO connection file built with the IO connection editor.

This file may also be generated by another tool, such as your

configuration tool.

There is no imposed format for auxiliary parameters put in a

separate data base. The only important item is to establish the link

between both data base.

The easiest way to complete IO description is to use the

slot/channel numbers to make the link between the standard ISaGRAF

connection information and the other data base. A configuration

tool can be used to build this link, and group IO variables on the

ISaGRAF boards. This tool can generate both ISaGRAF connection file

and separate data base.

Just remember that:

- The Workbench IO connection file is absolutely needed for

code generation

- One ISaGRAF board groups variables with same type and direction.

OEM parameters may also be used as a reference to establish the link

between data bases.

If your configuration tool is run to generate IO variable connection

file, use this information to initiate a new project, so that IO

variables and IO connection are already declared. Nothing has to be

changed in the ISaGRAF Workbench.

At run time, access to the separate data base is made in the OEM

interface. Nothing has to be modified or adapted in the ISaGRAF

target kernel.

____________________________________________________________________